Skip to content

chore(deps): bump wrangler to 4.158.0, @astrojs/cloudflare to 14.4.4 and astro to 7.4.7 - #151

Merged
Madraka merged 2 commits into
mainfrom
chore/wrangler-4-158
Nov 7, 2026
Merged

Madraka merged 2 commits into
mainfrom
chore/wrangler-4-158

Conversation

@Madraka

@Madraka Madraka commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

What

Lands Dependabot's #139 (@astrojs/cloudflare 14.3.4 → 14.4.4) together with the wrangler bump it needs. #139 stayed red after its rebase because @astrojs/cloudflare 14.4 resolves @cloudflare/vite-plugin 1.67.0, whose peer range is wrangler ^4.156.1, while main has 4.152.0; every astro build in packages/cli's Cloudflare suites then aborts with "The installed version of Wrangler (4.152.0) does not satisfy the peer dependency required by @cloudflare/vite-plugin (^4.156.1)".

  • pnpm-workspace.yaml catalog: wrangler 4.152.0 → 4.158.0 (latest 4.x, published 2026-11-05), @astrojs/cloudflare 14.3.4 → 14.4.4.
  • starters/blog/package.json: wrangler ^4.152.0 → ^4.158.0 (what a new project gets).
  • Resolved: @cloudflare/vite-plugin 1.67.0; wrangler's bundled Miniflare moves to 5.20261104.0-beta (the direct miniflare devDependency stays 4.20260730.0, ADR-0012). sharp resolves to 0.35.5 only; the override stays.
  • Astro 7.3.6 → 7.4.7: @astrojs/cloudflare 14.4.4 declares peer astro ^7.4.0, so the npm smoke job hit ERESOLVE on the packed starter. The catalog takes ^7.4.7, and the astro peer range of @cloudhal/astro-renderer and @cloudhal/cli moves from ^7.3.0 to ^7.4.0 (Starlight 0.42.6 wants ^7.2.10, satisfied).
  • AGENTS.md Versions line (wrangler 4.158, @astrojs/cloudflare 14.4, Astro 7.4), ADR-0012 note, and .changeset/deps-wrangler-4-158.md (patch for @cloudhal/astro-renderer, @cloudhal/cli, @cloudhal/cloudflare).

Pre-existing, not changed here: pnpm peers check reports @cloudflare/workers-types 5.20261007.1 (pinned, with a minimumReleaseAgeExclude entry) below wrangler's peer range — 4.152 already wanted ^5.20261019.1, 4.158 wants ^5.20261104.1 (latest is 5.20261107.1). Bumping workers-types is a separate decision.

Verified locally: pnpm install, pnpm lint (0 errors), pnpm typecheck. The deploy dry-run and workerd suites run in CI only (no local test suites while other sessions are running). For the owner to review; not merged by the agent. Closes #139 when merged.

Checklist

  • pnpm check and cargo test --workspace pass locally — relying on CI (lint and typecheck pass locally)
  • Contract change? pnpm gen was run and generated files are committed (docs/adr/0001) — n/a
  • User-visible change in a published package? pnpm changeset added
  • Commits are signed off (git commit -s, DCO)
  • Docs / AGENTS.md updated if behaviour or commands changed

🤖 Generated with Claude Code

Madraka and others added 2 commits November 8, 2026 01:50
The two move together: @astrojs/cloudflare 14.4 resolves
@cloudflare/vite-plugin 1.67.0, whose peer range is wrangler ^4.156.1,
which is why Dependabot's #139 stayed red after its rebase on
wrangler 4.152.0. The catalog takes 4.158.0 (latest 4.x), the blog
starter asks for ^4.158.0, and AGENTS.md, ADR-0012 and a changeset for
@cloudhal/astro-renderer, @cloudhal/cli and @cloudhal/cloudflare
follow.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
Signed-off-by: Madraka <[email protected]>
@astrojs/cloudflare 14.4.4 declares peer astro ^7.4.0, so the packed
starter's npm install hit ERESOLVE against astro 7.3.6 in the smoke
job. The catalog takes astro ^7.4.7, and the astro peer range of
@cloudhal/astro-renderer and @cloudhal/cli moves to ^7.4.0.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
Signed-off-by: Madraka <[email protected]>
@Madraka Madraka changed the title chore(deps): bump wrangler to 4.158.0 and @astrojs/cloudflare to 14.4.4 chore(deps): bump wrangler to 4.158.0, @astrojs/cloudflare to 14.4.4 and astro to 7.4.7 Nov 7, 2026
@Madraka
Madraka merged commit 0405733 into main Nov 7, 2026
6 checks passed
@Madraka
Madraka deleted the chore/wrangler-4-158 branch November 7, 2026 23:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant